Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0923

reference
396-tree-1
name
0923
tree-preservation-order

undefined

396-tpo-1
uprn
address-text
point
POINT (-1.016208 50.894573)
geometry
MULTIPOLYGON (((-1.016123 50.894563,-1.016127 50.894580,-1.016139 50.894595,-1.016158 50.894607,-1.016181 50.894615,-1.016207 50.894618,-1.016234 50.894616,-1.016258 50.894608,-1.016277 50.894597,-1.016289 50.894582,-1.016294 50.894565,-1.016290 50.894548,-1.016278 50.894533,-1.016260 50.894521,-1.016236 50.894513,-1.016210 50.894510,-1.016183 50.894513,-1.016159 50.894520,-1.016140 50.894532,-1.016128 50.894547,-1.016123 50.894563)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL